<%
=begin
apps: aspnet-core
platforms: kubernetes, tanzu-application-catalog
id: deploy_extra_resources
title: Deploy extra resources
category: administration
weight: 80
=end %>

There are cases where you may want to deploy extra objects, such a *ConfigMap* containing your application configuration or some extra deployment with a micro service used by your app. For covering this case, the chart allows adding the full specification of other objects using the *extraDeploy* parameter. The following example would create a *ConfigMap* including some application configuration. The application will be mounted in the ASP.NET Core application container:

~~~
extraDeploy:
  - |
    apiVersion: v1
    kind: ConfigMap
    metadata:
      name: aspnet-core-configuration
      labels: {{- include "common.labels.standard" . | nindent 6 }}
        {{- if .Values.commonLabels }}
        {{- include "common.tplvalues.render" ( dict "value" .Values.commonLabels "context" $ ) | nindent 6 }}
        {{- end }}
      {{- if .Values.commonAnnotations }}
      annotations: {{- include "common.tplvalues.render" ( dict "value" .Values.commonAnnotations "context" $ ) | nindent 6 }}
      {{- end }}
    data:
      appsettings.json: |-
        {
          "AllowedHosts": "*"
        }
extraVolumeMounts:
  - name: configuration
    mountPath: /app/config/
    readOnly: true
extraVolumes:
  - name: configuration
    configMap:
      name: aspnet-core-configuration
~~~
